ci: disable semantic-release github comment/label hooks#80
Merged
Conversation
The @semantic-release/github post-publish "success" hook walks every #N reference in the release notes and resolves each via GraphQL repository.issue(number:). That resolver only finds issues, not pull requests, so any commit body that references a PR by #N (e.g. "PRs #70-#77") causes a NOT_FOUND error after the release is already published — surfacing as a spurious workflow failure. Setting successComment, failComment, and releasedLabels to false disables the comment/label features (which the project does not rely on) and removes the failure mode. Artifact publishing, tagging, and the CHANGELOG/version-bump commit are unaffected. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The release workflow on the last two merges to
mainreported "all jobs failed" even thoughv0.12.1andv0.12.2were both fully published (tag, GitHub release, wheel + sdist all uploaded). The non-zero exit came from the post-publishsuccesshook of@semantic-release/github:@semantic-release/githubwalks every#Ntoken in the generated release notes and tries to look each one up via GraphQLrepository.issue(number: N). That resolver only finds issues, not pull requests. My PR #79 commit body referenced PRs#70–#77(the closed Dependabot PRs), and the lookup 404'd after publish, breaking the workflow exit code.This PR sets three options on
@semantic-release/githubso the same class of failure cannot happen again:successCommentfalsefailCommentfalsereleasedLabelsfalseArtifact publishing, tagging, the CHANGELOG/version-bump commit, and the conventional-commit-driven release decision are all unaffected — those happen earlier in the pipeline.
Test plan
.releaserc.jsonparses as valid JSON.mainexits zero (no follow-up "all jobs failed" notification).The commit is typed
ci:so semantic-release will not cut a release for this change itself.🤖 Generated with Claude Code